Method and device for configuring gtp transmission channel and storage medium

ABSTRACT

The present disclosure discloses a method for configuring a General Packet Radio Service Tunneling Protocol (GTP) transmission channel, including: acquiring, by a User Plane Centralized Unit (CU-U) responsible for user plane data in a first network element, session related information through an Xn interface, where the Xn interface is an interface between the CU-U and a Control Plane Centralized Unit (CU-C) responsible for control plane data in the first network element; performing a GTP transmission channel configuration by using the session related information; transmitting first related information of a local GTP transmission channel configuration to a second network element; and receiving second related information of a GTP transmission channel configuration transmitted by the second network element. The present disclosure also discloses an apparatus for configuring a GTP transmission channel.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is proposed based on a Chinese PatentApplication No. 201710074464.0 filed on Feb. 10, 2017, and claimspriority to the Chinese Patent Application, the content of which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the field of wireless communications,and in particular, to a method and apparatus for configuring a GPRSTunneling Protocol (GTP) transmission channel, and a storage medium.

BACKGROUND

In the Fifth Generation (5G) mobile communication system, a large numberof connections and higher rate requirements of users pose a greatchallenge for the transmission capacity of the fronthaul interface,i.e., the Common Public Radio Interface (CPRI), between the Base StationProcessing Unit (BBU) and the Remote Radio Unit (RRU) in the Long TermEvolution (LTE) system. Since the CPRI transmits IQ signals subjected toprocessing of physical layer coded modulation and the like, the CPRI hashigher requirements on transmission delay and bandwidth.

When the 5G air interface rate is increased to tens of Gbps, the trafficdemand of the CPRI required to be upgraded to the Tbps level, which putstremendous pressure on network deployment costs and deploymentdifficulty. Therefore, in the 5G system, it is beneficial to redefine adivision mode of the fronthaul interface. During division of thefronthaul interface, it is to be considered from several aspects of—thetransmission capacity, transmission delay, easy deployment and the like.For example, during the non-ideal fronthaul transmission, a firstnetwork element (for example a Centralized Unit (CU)) is endowed with adelay-insensitive network function, and a second network element (forexample a Distributed Unit (DU)) is endowed with a delay-sensitivenetwork function. As shown in FIG. 1, the first network element and thesecond network element are transmitted through an ideal and/or non-idealfronthaul interface, the interface is called a forward interface.

A first protocol entity (such as a Radio Resource Control (RRC) entity)may be located in the first network element. The first protocol entitygenerates control signaling, maintains at least one of establishment,modification, and release of a radio bearer, and maintains update of asecond protocol entity, a third protocol entity, a fourth protocolentity, and physical layer parameters. The function of the secondprotocol entity is similar to the Packet Data Convergence Protocol(PDCP) function of an LTE system and enhancement thereof, and a user maydefine multiple PDCP entities, and may configure each PDCP entitycarrying user plane data. Each PDCP entity carries data of one radiobearer, and the PDCP entity corresponds to a control plane or a userplane according to different data carried by the radio bearer. Thefunction of the third protocol entity is similar to the Radio LinkControl (RLC) function of the LTE system and enhancement thereof. Thefunction of the fourth protocol entity is similar to the Media AccessControl (MAC) function of the LTE system and enhancement thereof. Thesecond network element includes at least one of the following: thesecond protocol entity, the third protocol entity, the fourth protocolentity, a Physical Layer (PHY), and a Radio Frequency Unit (RF). Thefirst network element communicates with the second network elementthrough the fronthaul interface, and the possible functional division ofthe CU-DU split is as shown in FIG. 2.

In practical application, for option 2 of the function shown in FIG. 2,as shown in FIG. 3, there is another possibility that the control planePDCP entity and the user plane PDCP entity in the CU are separated, thatis, two PDCPs responsible for the user plane and the control plane arelocated in two different CUs, respectively. For the sake of description,the two CUs are respectively referred to as a User Plane CentralizedUnit (CU-U) and a Control Plane Centralized Unit (CU-C), therebyrealizing split of control plane data from user plane data.

An Xn interface exists between the CU-C and the CU-U. A forwardinterface NGx exists between the CU and the DU. The interface betweenthe CU-C and the DU is called NGx-C, and the interface between the CU-Uand the DU is called NGx-U.

SUMMARY

Embodiments of the present disclosure provide a method and apparatus forconfiguring a GTP transmission channel, and a storage medium.

The technical solutions of the embodiments of the present disclosure areimplemented as follows.

An embodiment of the present disclosure provides a method forconfiguring a GTP transmission channel. The method includes: acquiringsession related information through an Xn interface, where the Xninterface being used for interaction between a CU-U responsible for userplane data in a first network element and a CU-C responsible for controlplane data in the first network element; performing a GTP transmissionchannel configuration by using the session related information;transmitting first related information of a local GTP transmissionchannel configuration to a second network element; and receiving secondrelated information of a GTP transmission channel configurationtransmitted by the second network element.

In the foregoing solution, the acquired session related information issession related information in the session establishment process. Thestep of performing a GTP transmission channel configuration by using thesession related information includes: performing user planeconfiguration by using the session related information. The firstrelated information is GTP transmission channel configurationinformation transmitted by local user plane data. The second relatedinformation is GTP transmission channel configuration informationtransmitted by local user plane data of the second network elementcorresponding to the first related information.

In the foregoing solution, the acquired session related information issession related information in the session modification process. Thestep of performing a GTP transmission channel configuration by using thesession related information includes: modifying the user planeconfiguration by using the session related information. Correspondingly,the first related information is GTP transmission channel configurationmodification information transmitted by the local user plane data, andthe second related information is GTP transmission channel configurationmodification information transmitted by the local user plane data of thesecond network element corresponding to the first related information.

In the foregoing solution, the acquired session related information issession related information in the session deletion process. The step ofperforming a GTP transmission channel configuration by using the sessionrelated information includes: deleting a GTP transmission channelconfiguration by using the session related information. Correspondingly,the first related information is GTP transmission channel configurationdeletion information transmitted by the local user plane data, and thesecond related information is GTP transmission channel configurationdeletion acknowledgement information transmitted by the local user planedata of the second network element corresponding to the first relatedinformation.

In the foregoing solution, the step of transmitting first relatedinformation of a local GTP transmission channel configuration to asecond network element includes: directly sending the first relatedinformation to the second network element. Correspondingly, the step ofreceiving second related information of the GTP transmission channelconfiguration transmitted by the second network element includes:receiving the second related information directly sent by the secondnetwork element.

In the foregoing solution, the step of transmitting first relatedinformation of a local GTP transmission channel configuration to asecond network element includes: forwarding the first relatedinformation to the second network element through the CU-C.Correspondingly, the step of receiving second related information of theGTP transmission channel configuration transmitted by the second networkelement includes: receiving the second related information sent by thesecond network element and forwarded by the CU-C.

An embodiment of the present disclosure also provides a GTP transmissionchannel configuration method, including: acquiring session relatedinformation from a core network; and sending the session relatedinformation to a CU-U responsible for user plane data in a first networkelement through an Xn interface, where the session related informationis used by the CU-U to perform a GTP transmission channel configuration,and the Xn interface is used for interaction between the CU-U and a CU-Cresponsible for control plane data in the first network element.

In the foregoing solution, the step of acquiring session relatedinformation from a core network includes: acquiring the session relatedinformation from a core network through an NG interface, where the NGinterface is used for interaction between the CU-C and the core network.

In the foregoing solution, the method further includes: receiving firstrelated information of a local GTP transmission channel configuration ofthe CU-U sent by the CU-U, and forwarding the first related informationto a second network element; and receiving second related information ofa local GTP transmission channel configuration of the second networkelement sent by the second network element, and forwarding the secondrelated information to the CU-U.

An embodiment of the present disclosure provides an apparatus forconfiguring a GTP transmission channel. The apparatus includes: a firstacquiring unit, a configuration unit and a transmission unit.

The first acquiring unit is configured to acquire session relatedinformation through an Xn interface, the Xn interface being used forinteraction between a CU-U responsible for user plane data in a firstnetwork element and a CU-C responsible for control plane data in thefirst network element.

The configuration unit is configured to perform a GTP transmissionchannel configuration by using the session related information.

The transmission unit is configured to transmit first relatedinformation of a local GTP transmission channel configuration to asecond network element, and receive second related information of a GTPtransmission channel configuration transmitted by the second networkelement.

In the foregoing solution, the acquired session related information issession related information in the session establishment process. Theconfiguration unit is configured to: perform user plane configuration byusing the session related information. Correspondingly, the firstrelated information is GTP transmission channel configurationinformation transmitted by the local user plane data, and the secondrelated information is GTP transmission channel configurationinformation transmitted by the local user plane data of the secondnetwork element corresponding to the first related information.

In the foregoing solution, the acquired session related information issession related information in the session modification process. Theconfiguration unit is configured to: modify the user plane configurationby using the session related information. Correspondingly, the firstrelated information is GTP transmission channel configurationmodification information transmitted by the local user plane data, andthe second related information is GTP transmission channel configurationmodification information transmitted by the local user plane data of thesecond network element corresponding to the first related information.

In the foregoing solution, the acquired session related information issession related information in the session deletion process. Theconfiguration unit is configured to: delete a GTP transmission channelconfiguration by using the session related information. Correspondingly,the first related information is GTP transmission channel configurationdeletion information transmitted by the local user plane data, and thesecond related information is GTP transmission channel configurationdeletion acknowledgement information transmitted by the local user planedata of the second network element corresponding to the first relatedinformation.

In the foregoing solution, the transmission unit is configured to:directly send the first related information to the second networkelement; and receive the second related information directly sent by thesecond network element.

In the foregoing solution, the transmission unit is configured to:forward the first related information to the second network elementthrough the CU-C; and receive the second related information sent by thesecond network element and forwarded by the CU-C.

An embodiment of the present disclosure also provides an apparatus forconfiguring a GTP transmission channel. The apparatus includes a secondacquiring unit and a sending unit.

The second acquiring unit is configured to acquire session relatedinformation from a core network.

The sending unit is configured to send the session related informationto a CU-U responsible for user plane data in a first network elementthrough an Xn interface, where the session related information is usedby the CU-U to perform a GTP transmission channel configuration, and theXn interface is used for interaction between the CU-U and a CU-Cresponsible for control plane data in the first network element.

In the foregoing solution, the second acquiring unit is specificallyconfigured to: acquire the session related information from a corenetwork through an NG interface, where the NG interface is used forinteraction between the CU-C and the core network.

In the foregoing solution, the apparatus further includes: a receivingunit configured to receive first related information of a local GTPtransmission channel configuration of the CU-U sent by the CU-U, andreceive second related information of a local GTP transmission channelconfiguration of the second network element sent by the second networkelement.

The sending unit is configured to forward the first related informationto a second network element, and forward the second related informationto the CU-U.

An embodiment of the present disclosure also provides a storage medium,which stores computer programs for, when executed by a processor,implementing the above steps of any one method at the CU-U responsiblefor user plane data in the first network element, or the above steps ofany one method at the CU-C responsible for control plane data in thefirst network element.

According to the method and apparatus for configuring a GTP transmissionchannel and the storage medium provided by the embodiments of thepresent disclosure, the CU-C acquires session related information fromthe core network, the CU-U acquires session related information throughan Xn interface, the Xn interface being used for interaction between theCU-U and the CU-C, the CU-U performs a GTP transmission channelconfiguration by using the session related information, and transmitsfirst related information of a local GTP transmission channelconfiguration to the second network element, and the CU-U receivessecond related information of a GTP transmission channel configurationtransmitted by the second network element, so that the configuration ofthe GTP transmission channel between the CU-U and the DU is achievedthrough the Xn interface.

BRIEF DESCRIPTION OF DRAWINGS

In the drawings, which are not necessarily to scale, similar referencenumerals may describe similar parts in different views. The drawingsgenerally illustrate the various embodiments discussed herein by way ofexample instead of limitation.

FIG. 1 is a schematic diagram of a fronthaul interface between a firstnetwork element and a second network element according to an embodimentof the present disclosure;

FIG. 2 is a schematic diagram of possible functional division between afirst network element and a second network element according to anembodiment of the present disclosure;

FIG. 3 is a schematic diagram showing split of control plane data anduser plane data of a first network element according to an embodiment ofthe present disclosure;

FIG. 4 is a schematic flowchart of a method for configuring a GTPtransmission channel for a CU-U according to Embodiment 1 of the presentdisclosure;

FIG. 5 is a schematic flowchart of a method for configuring a GTPtransmission channel for a CU-C according to Embodiment 1 of the presentdisclosure;

FIG. 6 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 1 of the presentdisclosure;

FIG. 7 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 2 of the presentdisclosure;

FIG. 8 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 3 of the presentdisclosure;

FIG. 9 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 4 of the presentdisclosure;

FIG. 10 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 5 of the presentdisclosure;

FIG. 11 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 6 of the presentdisclosure;

FIG. 12 is a schematic flowchart of a method for configuring a GTPtransmission channel according to Embodiment 7 of the presentdisclosure;

FIG. 13 is a schematic structural diagram of an apparatus forconfiguring a GTP transmission channel disposed at a CU-U according toEmbodiment 8 of the present disclosure;

FIG. 14 is a schematic structural diagram of an apparatus forconfiguring a GTP transmission channel disposed at a CU-C according toEmbodiment 8 of the present disclosure;

FIG. 15 is a schematic structural diagram of a system for configuring aGTP transmission channel according to Embodiment 8 of the presentdisclosure; and

FIG. 16 is a schematic diagram of an application scenario of a solutionaccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION

The present disclosure will be further described in detail below withreference to the accompanying drawings and embodiments.

The interaction between the first network element and the second networkelement in the 5G system is first comprehended prior to describing theembodiments of the present disclosure.

For the first network element and the second network element, functionsof a base station are virtually divided and performed by the firstnetwork element and the second network element. That is, the firstnetwork element is a logic node that implements part of the functions ofthe base station, and the second network element is a logic node thatimplements other functions except those implemented by the first networkelement, and the first network element can control the second networkelement.

As shown in FIG. 1, information is exchanged between the first networkelement and the second network element through the fronthaul interface.For different delay requirements, the fronthaul interface may be anideal fronthaul interface or a non-ideal fronthaul interface. Thetransmission delay of the ideal fronthaul interface is relatively small,such as about tens to hundreds of microseconds, and the transmissiondelay of the non-ideal fronthaul interface is relatively large, such asmilliseconds, due to the distinction between ideal and non-idealfronthaul interfaces, the first network element and the second networkelement have different functional divisions.

FIG. 2 is a diagram illustrating possible functional division betweenthe first network element and the second network element. Specificpossible functional division solutions are as follows:

1. Option 1 (RRC/PDCP split):

In this functional split option, the RRC is located in the CU (i.e., thefirst network element), and functions such as PDCP, RLC, MAC, PHY, andRF are all located in the DU (i.e., the second network element). Thatis, the entire Upper (UP) function is located in the DU.

2. Option 2 (PDCP/RLC split):

In this functional split option, the RRC and the PDCP are located in theCU, and functions such as RLC, MAC, PHY, and RF are all located in theDU.

3. Option 3 (High RLC/Low RLC split):

In this functional split option, low-layer RLC (part of the function ofthe RLC), MAC, PHY, and a part of RF are located in the DU, andfunctions such as PDCP and high-layer RLC (part of the functions of theRLC) are located in the CU.

4. Option 4 (RLC-MAC split):

In this functional split option, MAC, PHY, and part of RF are located inthe DU, and functions such as PDCP and RLC are all located in the CU.

5. Option 5 (Intra MAC split):

In this functional split option, part of the functions of the MAC (suchas Hybrid Automatic Repeat Request (HARQ)), PHY and part of RF arelocated in the DU, and other UP functions are located in the CU.

6. Option 6 (MAC-PHY split):

In this functional split option, MAC, PHY, and part of RF are located inthe DU, and functions such as PDCP and RLC are all located in the CU.

7. Option 7 (Intra PHY split):

In this functional split option, part of the functions of the MAC (suchas HARQ), PHY and part of RF are located in the DU, and other UPfunctions are located in the CU.

8. Option 8 (PHY-RF split):

In this functional split option, part of RF is located in the DU, andother UP functions are all located in the CU.

FIG. 3 is a schematic diagram showing split of user plane data andcontrol plane data of the first network element. As shown in FIG. 3, twoPDCPs of the user plane and the control plane are respectively locatedin two different CUs. For the sake of description, the two CUs arerespectively referred to as a CU-U and a CU-C, thereby realizing splitof user plane data and control plane data. An Xn interface existsbetween the CU-C and the CU-U. A forward interface NGx exists betweenthe CU and the DU. The interface between the CU-C and the DU is calledNGx-C, and the interface between the CU-U and the DU is called NGx-U.

In various embodiments of the present disclosure, acquiring, by theCU-U, session related information through an Xn interface, the Xninterface being an interface between the CU-U and a Control PlaneCentralized Unit (CU-C) responsible for control plane data in the firstnetwork element, performing a GTP transmission channel configuration byusing the session related information, transmitting first relatedinformation of a local GTP transmission channel configuration to asecond network element, and receiving second related information of aGTP transmission channel configuration transmitted by the second networkelement so as to complete the GTP transmission channel configuration.

Embodiment 1

An embodiment of the present disclosure provides a method forconfiguring a GTP transmission channel, applied to a CU-U responsiblefor user plane data in a first network element. As shown in FIG. 4, themethod includes:

In step 401: Session related information is acquired through an Xninterface.

Here, the Xn interface is an interface between the CU-U and the CU-Cresponsible for control plane data in the first network element. Thatis, the Xn interface is used for interaction between the CU-U and theCU-C.

In other words, the CU-U acquires the session related information fromthe CU-C through the Xn interface.

Specifically, the session related information sent by the CU-C isreceived by the Xn interface.

The specific content of the session related information is slightlydifferent according to different application scenarios.

Specifically, when the session related information is session relatedinformation in the session establishment process, the session relatedinformation includes GTP channel information and PDU session informationrequired for establishing a current Protocol Data Unit (PDU) session.

When the session related information is session related information inthe session modification process, the session related informationincludes GTP channel information and PDU session information requiredfor modifying the current PDU session.

When the session related information is session related information inthe session deletion process, the session related information includesinformation required for deleting the current PDU session.

In step 402: A GTP transmission channel configuration is performed byusing the session related information.

Specifically, when the acquired session related information is sessionrelated information in the session establishment process, the user planeconfiguration is performed by using the session related information.

When the acquired session related information is session relatedinformation in the session modification process, the session relatedinformation is used to modify the user plane configuration.

When the acquired session related information is session relatedinformation in the session deletion process, the GTP transmissionchannel configuration is deleted by using the session relatedinformation.

In step 403: First related information of a local GTP transmissionchannel configuration is transmitted to a second network element.

In step 404: Second related information of a GTP transmission channelconfiguration transmitted by the second network element is received.

Here, when the acquired session related information is session relatedinformation in the session establishment process, the first relatedinformation is GTP transmission channel configuration informationtransmitted by local user plane data, and the second related informationis the GTP transmission channel configuration information transmitted bythe local user plane data of the second network element corresponding tothe first related information.

When the acquired session related information is session relatedinformation in the session modification process, the first relatedinformation is GTP transmission channel configuration modificationinformation transmitted by the local user plane data, and the secondrelated information is the GTP transmission channel configurationmodification information transmitted by the local user plane data of thesecond network element corresponding to the first related information.

When the acquired session related information is session relatedinformation in the session deletion process, the first relatedinformation is GTP transmission channel configuration deletioninformation transmitted by the local user plane data, and the secondrelated information is the GTP transmission channel configurationdeletion acknowledgement information transmitted by the local user planedata of the second network element corresponding to the first relatedinformation.

In practical applications, there are two implementation modes for theconfiguration of the GTP transmission channel between the CU-U and theDU: one mode is that the CU-U and the DU configure the GTP transmissionchannel by themselves, and the other mode is that the CU-C assists theCU-U and the DU in configuring the GTP transmission channel.

In the first mode, the specific implementation of step 403 includes:directly sending, by the CU-U, the first related information to thesecond network element.

Accordingly, the specific implementation of step 404 includes:receiving, by the CU-U, the second related information directly sent bythe second network element.

In the second mode, the specific implementation of step 403 includes:forwarding, by the CU-U, the first related information to the secondnetwork element through the CU-C.

Accordingly, the specific implementation of step 404 includes:receiving, by the CU-U, the second related information sent by thesecond network element and forwarded by the CU-C.

Accordingly, an embodiment of the present disclosure also provides amethod for configuring a GTP transmission channel, applied to the CU-C.As shown in FIG. 5, the method includes:

In step 501: Session related information is acquired from a corenetwork.

Specifically, the CU-C acquires the session related information from theNG interface through the NG interface.

The NG interface is an interface between the core network and the CU-C,that is, the NG interface is used for interaction between the corenetwork and the CU-C.

In step 502: The session related information is sent to a CU-Uresponsible for user plane data in a first network element through an Xninterface.

Here, the session related information is used by the CU-U to configurethe GTP transmission channel, that is, steps 402-404 are executed.

In the process that the CU-C assists the CU-U and the DU in configuringthe GTP transmission channel, the CU-C is required to participate in theforwarding of a message.

On this basis, in an embodiment, the method may also include: receiving,by the CU-C, first related information of a local GTP transmissionchannel configuration of the CU-U sent by the CU-U, and forwarding thefirst related information to a second network element; and receiving, bythe CU-C, second related information of a local GTP transmission channelconfiguration of the second network element sent by the second networkelement, and forwarding the second related information to the CU-U.

An embodiment of the present disclosure also provides a method forconfiguring a GTP transmission channel. As shown in FIG. 6, the methodincludes:

In step 601: A CU-C acquires session related information from a corenetwork.

In step 602: The CU-C sends the session related information to a CU-Uresponsible for user plane data in a first network element through an Xninterface.

In step 603: The CU-U performs GTP transmission channel configuration byusing the session related information.

In step 604: The CU-U transmits first related information of the localGTP transmission channel configuration to a second network element.

In step 605: The CU-U receives second related information of the GTPtransmission channel configuration transmitted by the second networkelement.

Here, it should be noted that the specific processing procedures of theCU-U and the CU-C are described in detail above, and details are notdescribed herein.

The functions of the first network element and the second networkelement may be understood by referring to the foregoing description.

According to the method for configuring a GTP transmission channelprovided by the embodiments of the present disclosure, the CU-C acquiressession related information from the core network, the CU-U acquiressession related information through an Xn interface, the Xn interface isused for interaction between the CU-U and the CU-C, the CU-U performs aGTP transmission channel configuration by using the session relatedinformation, and transmits first related information of a local GTPtransmission channel configuration to the second network element, andthe CU-U receives second related information of a GTP transmissionchannel configuration transmitted by the second network element, so thatthe configuration of the GTP transmission channel on an NG-U interfacebetween the CU-U and the DU is achieved through the Xn interface,thereby implementing split of control signaling and user data, andsupporting an independent user plane data transmission function whilehaving the centralized RRC/Radio Resource Management (RRM) function.

Embodiment 2

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-U and the DU configure a GTP transmission channel when aPDU session is established. As shown in FIG. 7, the process includes:

In step 701: A Next Generation Core (NGC) sends a PDU sessionestablishment request to a CU-C.

Here, the PDU session establishment request carries PDU session relatedinformation. That is, the CU-C acquires PDU session related informationfrom the NGC through the PDU session establishment procedure of the NGinterface.

The related information includes GTP channel information and PDU sessioninformation required for establishing a current PDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of a core network UP Gateway (GW) (if the user planetransport layer adopts a GTP-U protocol, transport layer IP addressinformation and a GTP Tunnel Endpoint Identifier (TEID) are included), asession ID, one or more flow IDs in a single session, QoS relatedinformation of a Non-GBR service corresponding to the flow, and QoSrelated information of a GBR service corresponding to the flow.

Further, if the GTP channel of the flow level is allowed to beestablished, transport layer address information of the core network UPGW corresponding to all flows in the current PDU session is included (ifthe user plane transport layer adopts the GTP-U protocol, the transportlayer IP address information and the GTP TEID are included).

In step 702: After receiving the request, the CU-C sends a PDU sessionestablishment request to a CU-U.

Here, the sent PDU session establishment request carries PDU sessionrelated information. That is, the CU-C transmits the PDU session relatedinformation acquired in step 1 to the CU-U through the Xn interface.

In step 703: After receiving the request, the CU-U sends GTP channelconfiguration information to a DU.

Specifically, after receiving the PDU session related information fromthe CU-C, the CU-U performs the user plane configuration and sends theGTP channel configuration information transmitted by the local userplane data to the DU through an interface message.

The sent GTP channel configuration information includes, but is notlimited to, transport layer address information of the CU-U (if the userplane transport layer adopts the GTP-U protocol, the transport layer IPaddress information and the GTP TEID are included).

In actual application, the interaction between the CU-U and the DU maybe implemented through an NGx AP message or a GTP message.

In step 704: After receiving the GTP channel configuration informationsent by the CU-U, the DU feeds back its GTP channel configurationinformation to the CU-U through a response message.

Here, the fed-back GTP channel configuration information includes, butis not limited to, transport layer address information of the DU (if theuser plane transport layer adopts the GTP-U protocol, the transportlayer IP address information and the GTP TEID are included).

In step 705: After receiving the GTP channel configuration informationof the DU, the CU-U feeds the PDU session information that the GTPchannel configuration succeeds back to the CU-C.

Here, if the CU-U receives the GTP channel configuration information ofthe DU, it is indicated that the GTP channel configuration between theCU-U and the DU succeeds.

If the GTP channel configuration information of the DU is not received,it is indicated that the GTP channel configuration between the CU-U andthe DU fails.

The fed-back PDU session information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the CU-U (if the user plane transport layer adopts theGTP-U protocol, the transport layer IP address information and the GTPTEID are included), a session ID, and one or more flow IDs that the userplane configuration succeeds in a single session.

When the GTP channel configuration between the CU-U and the DU fails,the fed-back PDU session information can include one or more flow IDsthat the user plane configuration fails, and corresponding failurereasons.

In step 706: The CU-C sends a PDU session establishment success messageto the NGC through the NG interface, and feeds the PDU sessioninformation that the GTP channel configuration succeeds back to the NGC.

Here, the PDU session information fed back to the NGC includes, but isnot limited to, one or more of the following information: transportlayer address information of the CU-U (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, and one or more flow IDsthat the user plane configuration succeeds in a single session.

When the GTP channel configuration between the CU-U and the DU fails,the PDU session information fed back to the NGC can include one or moreflow IDs that the user plane configuration fails, and correspondingfailure reasons.

Embodiment 3

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-U and the DU configure the GTP transmission channel whenthe PDU session is modified. As shown in FIG. 8, the process includes:

In step 801: An NGC sends a PDU session modification request to a CU-C.

Here, the PDU session modification request carries PDU sessionmodification related information. That is, the CU-C acquires PDU sessionmodification related information from the NGC through the PDU sessionmodification procedure of an NG interface.

The related information includes GTP channel information and PDU sessioninformation required for modifying the current PDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the core network UP GW (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, one or more flow IDs to beadded in a single session, QoS related information of a Non-GBR servicecorresponding to the flow, QoS related information of a GBR servicecorresponding to the flow, one or more flow IDs to be modified in asingle session, QoS related information of the Non-GBR servicecorresponding to the flow, QoS related information of the GBR servicecorresponding to the flow, and one or more flow IDs to be deleted in asingle session.

In step 802: After receiving the request, the CU-C sends a PDU sessionmodification request to a CU-U.

Here, the sent PDU session modification request carries the modified PDUsession related information. That is, the CU-C transmits the modifiedPDU session related information to the CU-U through the PDU sessionmodification procedure of an Xn interface.

The transmitted PDU session related information includes GTP channelinformation and PDU session information required for modifying thecurrent PDU session.

In step 803: After receiving the request, the CU-U sends the GTP channelmodification information to a DU.

Specifically, after receiving the modified PDU session relatedinformation from the CU-C, the CU-U performs modification (such asaddition, modification, or deletion) on the user plane configuration,and sends the modified local GTP channel configuration modificationinformation for user plane transmission to the DU through an interfacemessage.

The sent GTP channel configuration modification information includes,but is not limited to, transport layer address information of the CU-U(if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included).

In actual application, the interaction between the CU-U and the DU maybe implemented through an NGx AP message or a GTP message.

In step 804: After receiving the GTP channel configuration modificationinformation sent by the CU-U, the DU feeds back its GTP channelconfiguration modification information to the CU-U through a responsemessage.

Here, the fed-back GTP channel configuration modification informationincludes, but is not limited to, transport layer address information ofthe DU (if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included).

In step 805: After receiving the GTP channel configuration modificationinformation of the DU, the CU-U feeds the PDU session information thatthe GTP channel configuration modification succeeds back to the CU-C.

Here, if the CU-U receives the GTP channel configuration modificationinformation of the DU, it is indicated that the GTP channelconfiguration modification between the CU-U and the DU succeeds, and theCU-U feeds the PDU session information that the GTP channelconfiguration modification succeeds back to the CU-C.

The fed-back PDU session information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the CU-U (if the user plane transport layer adopts theGTP-U protocol, the transport layer IP address information and the GTPTEID are included), a session ID, and one or more flow IDs for userplane configuration modification in a single session.

When the GTP channel configuration modification between the CU-U and theDU fails, the fed-back PDU session information optionally includes oneor more flow IDs that the user plane configuration modification fails,and corresponding failure reasons.

In step 806: The CU-C sends a PDU session modification success messageto an NGC through an NG interface, and feeds the PDU session informationthat the GTP channel configuration modification succeeds back to theNGC.

Here, the PDU session information fed back to the NGC includes, but isnot limited to, one or more of the following information: transportlayer address information of the CU-U (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, and one or more flow IDsthat the user plane configuration succeeds in a single session.

When the GTP channel configuration modification between the CU-U and theDU fails, the PDU session information fed back to the NGC optionallyincludes one or more flow IDs that the user plane configuration fails,and corresponding failure reasons.

Embodiment 4

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-U and the DU configure the GTP transmission channel whenthe PDU session is deleted. As shown in FIG. 9, the process includes:

In step 901: An NGC sends a PDU session deletion request to a CU-C.

Here, the PDU session deletion request carries PDU session relatedinformation. That is, the CU-C acquires PDU session related informationfrom the NGC through the PDU session deletion procedure of the NGinterface.

The related information includes information required for deleting thePDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the core network UP GW (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TED are included), a session ID, and reasons for sessiondeletion.

In step 902: After receiving the request, the CU-C sends a PDU sessiondeletion request to a CU-U.

Here, the sent PDU session deletion request carries information requiredfor deleting the PDU session. That is, the CU-C transmits theinformation required for deleting the PDU session to the CU-U throughthe PDU session deletion procedure of the Xn interface.

The transmitted information required for deleting the PDU sessionincludes, but is not limited to, one or more of the followinginformation: transport layer address information of the core network UPGW (if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included), asession ID, and reasons for session deletion.

In step 903: After the request is received, the GTP channelconfiguration deletion information is sent to a DU.

Specifically, after receiving the related information of deleting thePDU session, the CU-U deletes the corresponding local GTP channelconfiguration information, and sends the GTP channel configurationdeletion information to the DU.

In step 904: After receiving the GTP channel configuration deletioninformation sent by the CU-U, the DU deletes the local GTP channelconfiguration information, and sends a GTP channel deletionacknowledgement message to the CU-U through a response message.

In step 905: After receiving the GTP channel deletion acknowledgementmessage from the DU, the CU-U sends a PDU session deletion successmessage to the CU-C.

Here, the sent message includes, but is not limited to, transport layeraddress information of the CU-U (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TED are included).

In step 906: After receiving the PDU session deletion success messagesent by the CU-U, the CU-C sends a PDU session deletion acknowledgementmessage to the NGC through the NG interface.

Embodiment 5

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-C assists the CU-U and the DU in configuring a GTPtransmission channel when a PDU session is established. As shown in FIG.10, the process includes:

In step 1001: An NGC sends a PDU session establishment request to aCU-C.

Here, the PDU session establishment request carries PDU session relatedinformation. That is, the CU-C acquires PDU session related informationfrom the NGC through the PDU session establishment procedure of the NGinterface.

The related information includes GTP channel information and PDU sessioninformation required for establishing a current PDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of a core network UP GW (if the user plane transport layeradopts a GTP-U protocol, transport layer IP address information and aGTP TEID are included), a session ID, one or more flow IDs in a singlesession, QoS related information of a Non-GBR service corresponding tothe flow, and QoS related information of a GBR service corresponding tothe flow.

Further, if the GTP channel of the flow level is allowed to beestablished, transport layer address information of the core network UPGW corresponding to all flows in the current PDU session is included (ifthe user plane transport layer adopts the GTP-U protocol, the transportlayer IP address information and the GTP TEID are included).

In step 1002: After receiving the request, the CU-C sends a PDU sessionestablishment request to a CU-U.

Here, the sent PDU session establishment request carries PDU sessionrelated information. That is, the CU-C transmits the PDU session relatedinformation acquired in step 1001 to the CU-U through an Xn interface.

In step 1003: After receiving the request, the CU-U sends the GTPchannel configuration information to the CU-C.

Specifically, the CU-U completes the local user plane configurationaccording to the received Xn interface message, and sends the locallyallocated GTP channel configuration information to the CU-C through aresponse message.

The sent GTP channel configuration information includes, but is notlimited to, transport layer address information of the CU-U (if the userplane transport layer adopts the GTP-U protocol, the transport layer IPaddress information and the GTP TEID are included).

In step 1004: After receiving the GTP channel configuration informationfrom the CU-U, the CU-C sends the configuration information to the DU.

Here, the sent GTP channel configuration information includes, but isnot limited to, transport layer address information of the CU-U (if theuser plane transport layer adopts the GTP-U protocol, the transportlayer IP address information and the GTP TEID are included).

In step 1005: After receiving the GTP channel configuration informationabout the CU-U forwarded by the CU-C, the DU feeds back its GTP channelconfiguration information to the CU-C.

Here, the GTP channel configuration information fed back to the CU-Cincludes, but is not limited to, transport layer address information ofthe DU (if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TEID are included).

In step 1006: After receiving the GTP channel configuration informationfrom the DU, the CU-C feeds back the GTP channel configurationinformation from the DU to the CU-U to complete GTP channelconfiguration.

Here, if the CU-U receives the GTP channel configuration information ofthe DU, it is indicated that the GTP channel configuration between theCU-U and the DU succeeds, and in this case, the CU-C feeds back the GTPchannel configuration modification information of the DU to the CU-Uthrough a GTP channel configuration success message.

If the GTP channel configuration information of the DU is not received,it is indicated that the GTP channel configuration between the CU-U andthe DU fails, and in this case, the CU-C sends a GTP channelconfiguration failure message and corresponding failure reasons to theCU-U.

In step 1007: The CU-C sends a PDU session establishment success messageto an NGC through an NG interface, and feeds the PDU session informationthat the GTP channel configuration succeeds back to the NGC.

Here, the PDU session information fed back to the NGC includes, but isnot limited to, one or more of the following information: transportlayer address information of the CU-U (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, and one or more flow IDsthat the user plane configuration succeeds in a single session.

When the GTP channel configuration between the CU-U and the DU fails,the PDU session information fed back to the NGC optionally includes oneor more flow IDs that the user plane configuration fails, andcorresponding failure reasons.

Embodiment 6

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-C assists the CU-U and the DU in configuring a GTPtransmission channel when the PDU session is modified. As shown in FIG.11, the process includes:

In step 1101: An NGC sends a PDU session modification request to a CU-C.

Here, the PDU session modification request carries PDU sessionmodification related information. That is, the CU-C acquires PDU sessionmodification related information from the NGC through the PDU sessionmodification procedure of an NG interface.

The related information includes GTP channel information and PDU sessioninformation required for modifying the current PDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the core network UP GW (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, one or more flow IDs to beadded in a single session, QoS related information of a Non-GBR servicecorresponding to the flow, QoS related information of a GBR servicecorresponding to the flow, one or more flow IDs to be modified in asingle session, QoS related information of the Non-GBR servicecorresponding to the flow, QoS related information of the GBR servicecorresponding to the flow, and one or more flow IDs to be deleted in asingle session.

In step 1102: After receiving the request, the CU-C sends a PDU sessionmodification request to a CU-U.

Here, the sent PDU session modification request carries the modified PDUsession related information. That is, the CU-C transmits the modifiedPDU session related information to the CU-U through the PDU sessionmodification procedure of an Xn interface.

The transmitted PDU session related information includes GTP channelinformation and PDU session information required for modifying thecurrent PDU session.

In step 1103: After receiving the request, the CU-U sends GTP channelconfiguration information to the CU-C.

Specifically, after receiving the modified PDU session relatedinformation from the CU-C, the CU-U performs modification (such asaddition, modification, or deletion) on the user plane configuration,and sends the modified local GTP channel configuration modificationinformation for user plane transmission to the CU-C through an interfacemessage.

The sent GTP channel configuration modification information includes,but is not limited to, transport layer address information of the CU-U(if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included).

In step 1104: After receiving the GTP channel configuration modificationinformation from the CU-U, the CU-C forwards the GTP channelconfiguration modification information to the DU.

Here, the GTP channel configuration modification information sent to theDU includes, but is not limited to, transport layer address informationof the CU-U (if the user plane transport layer adopts the GTP-Uprotocol, the transport layer IP address information and the GTP TEIDare included).

In step 1105: After receiving the GTP channel configuration modificationinformation about the CU-U forwarded by the CU-C, the DU feeds back itsGTP channel configuration modification information to the CU-C.

Here, the fed-back GTP channel configuration modification informationincludes, but is not limited to, transport layer address information ofthe DU (if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included).

In step 1106: After receiving the GTP channel configuration modificationinformation from the DU, the CU-C feeds back the GTP channelconfiguration modification information from the DU to the CU-U tocomplete GTP channel configuration modification.

Here, if the CU-U receives the GTP channel configuration information ofthe DU, it is indicated that the GTP channel configuration between theCU-U and the DU succeeds, and in this case, the CU-C feeds back the GTPchannel configuration modification information of the DU to the CU-Uthrough a GTP channel configuration modification success message.

If the CU-C fails to receive the GTP channel configuration modificationinformation from the DU, a GTP channel configuration failure message andcorresponding failure reasons are sent to the CU-U.

In step 1107: The CU-C sends a PDU session modification success messageto an NGC through an NG interface, and feeds the PDU session informationthat the GTP channel configuration modification succeeds back to theNGC.

Here, the PDU session information fed back to the NGC includes, but isnot limited to, one or more of the following information: transportlayer address information of the CU-U (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TEID are included), a session ID, and one or more flow IDsthat the user plane configuration succeeds in a single session.

When the GTP channel configuration modification between the CU-U and theDU fails, the PDU session information fed back to the NGC optionallyincludes one or more flow IDs that the user plane configuration fails,and corresponding failure reasons.

Embodiment 7

On the basis of Embodiment 1, this embodiment describes the process inwhich the CU-C assists the CU-U and the DU in configuring a GTPtransmission channel when a PDU session is deleted. As shown in FIG. 12,the process includes:

In step 1201: An NGC sends a PDU session deletion request to a CU-C.

Here, the PDU session deletion request carries PDU session relatedinformation. That is, the CU-C acquires PDU session related informationfrom the NGC through the PDU session deletion procedure of an NGinterface.

The related information includes information required for deleting thePDU session.

Specifically, the related information includes, but is not limited to,one or more of the following information: transport layer addressinformation of the core network UP GW (if the user plane transport layeradopts the GTP-U protocol, the transport layer IP address informationand the GTP TED are included), a session ID, and reasons for sessiondeletion.

In step 1202: After receiving the request, the CU-C sends a PDU sessiondeletion request to a CU-U.

Here, the sent PDU session deletion request carries information requiredfor deleting the PDU session. That is, the CU-C transmits theinformation required for deleting the PDU session to the CU-U throughthe PDU session deletion procedure of an Xn interface.

The transmitted information required for deleting the PDU sessionincludes, but is not limited to, one or more of the followinginformation: transport layer address information of the core network UPGW (if the user plane transport layer adopts the GTP-U protocol, thetransport layer IP address information and the GTP TED are included), asession ID, and reasons for session deletion.

In step 1203: After the request is received by the CU-C, GTP channelconfiguration deletion information is sent to the CU-C.

Specifically, after receiving the related information of deleting thePDU session, the CU-U deletes the corresponding local GTP channelconfiguration information, and sends the GTP channel configurationdeletion information to the CU-C.

The sent GTP channel configuration deletion information includes, but isnot limited to, transport layer address information of the CU-U (if theuser plane transport layer adopts the GTP-U protocol, the transportlayer IP address information and the GTP TED are included).

In step 1204: After receiving the GTP channel configuration deletioninformation from the CU-U, the CU-C forwards the GTP channelconfiguration deletion information to the DU.

In step 1205: After receiving the GTP channel configuration deletioninformation about the CU-U forwarded by the CU-C, the DU deletes thecorresponding local GTP channel configuration information, and sends aGTP channel configuration deletion acknowledgement message to the CU-Uthrough a response message.

In step 1206: After receiving the GTP channel configuration deletionacknowledgement message from the DU, the CU-C sends a PDU sessiondeletion acknowledgement message to an NGC through an NG interface.

Embodiment 8

To implement the method of the embodiments of the present disclosure,this embodiment provides an apparatus for configuring a GTP transmissionchannel, which is disposed in a CU-U responsible for user plane data ina first network element. As shown in FIG. 13, the apparatus includes: afirst acquiring unit 131, a configuration unit 132, and a transmissionunit 133.

The first acquiring unit 131 is configured to acquire session relatedinformation through an Xn interface, where the Xn interface is aninterface between the CU-U and a CU-C responsible for control plane datain a first network element, that is, the Xn interface is used forinteraction between the CU-U and the CU-C;

The configuration unit 132 is configured to perform a GTP transmissionchannel configuration by using the session related information.

The transmission unit 133 is configured to transmit first relatedinformation of a local GTP transmission channel configuration to asecond network element, and receive second related information of a GTPtransmission channel configuration transmitted by the second networkelement.

When the acquired session related information is session relatedinformation in the session establishment process, the configuration unit132 is configured to: perform user plane configuration by using thesession related information. The first related information is GTPtransmission channel configuration information transmitted by the localuser plane data, and the second related information is GTP transmissionchannel configuration information transmitted by the local user planedata of the second network element corresponding to the first relatedinformation.

When the acquired session related information is session relatedinformation in the session modification process, the configuration unit132 is configured to: modify the user plane configuration by using thesession related information. Correspondingly, the first relatedinformation is GTP transmission channel configuration modificationinformation transmitted by the local user plane data, and the secondrelated information is GTP transmission channel configurationmodification information transmitted by the local user plane data of thesecond network element corresponding to the first related information.

When the acquired session related information is session relatedinformation in the session deletion process, the configuration unit 132is configured to: delete GTP transmission channel configuration by usingthe session related information. Correspondingly, the first relatedinformation is GTP transmission channel configuration deletioninformation transmitted by the local user plane data, and the secondrelated information is GTP transmission channel configuration deletionacknowledge information transmitted by the local user plane data of thesecond network element corresponding to the first related information.

In practical applications, there are two implementation modes for theconfiguration of the GTP transmission channel between the CU-U and theDU: one mode is that the CU-U and the DU configure the GTP transmissionchannel by themselves, and the other mode is that the CU-C assists theCU-U and the DU in configuring the GTP transmission channel.

In the first mode, the transmission unit 133 is configured to: directlysend the first related information to the second network element; andreceive the second related information directly sent by the secondnetwork element.

In the second mode, the transmission unit 133 is configured to: forwardthe first related information to the second network element through theCU-C; and receive the second related information sent by the secondnetwork element and forwarded by the CU-C.

In practical applications, the first acquiring unit 131 and thetransmission unit 133 may be implemented by a communication interface ina configuration apparatus of a GTP transmission channel. Theconfiguration unit 132 may be implemented by a controller (such as aCentral Processing Unit (CPU), a Micro Control Unit (MCU), a DigitalSignal Processor (DSP), or a Field-Programmable Gate Array (FPGA)) inthe configuration apparatus of the GTP transmission channel.

In addition, those skilled in the art should understand that theimplementation functions of units in the apparatus shown in FIG. 13 maybe understood with reference to the related description of the foregoingmethod.

To implement the method of the embodiments of the present disclosure,this embodiment also provides an apparatus for configuring a GTPtransmission channel, which is disposed in a CU-C responsible forcontrol plane data in a first network element. As shown in FIG. 14, theapparatus includes: a second acquiring unit 141 and a sending unit 142.

The second acquiring unit 141 is configured to acquire session relatedinformation from a core network.

The sending unit 142 is configured to send the session relatedinformation to a CU-U responsible for user plane data in a first networkelement through an Xn interface, where the session related informationis used by the CU-U to perform a GTP transmission channel configuration.

The second acquiring unit 141 is configured to: acquire the sessionrelated information from a core network through an NG interface.

The NG interface is an interface between the core network and the CU-C,that is, the NG interface is used for interaction between the corenetwork and the CU-C.

In the process that the CU-C assists the CU-U and the DU in configuringthe GTP transmission channel, the CU-C is required to participate in theforwarding of a message.

On this basis, in an embodiment, the apparatus may also include areceiving unit.

The receiving unit is configured to receive first related information ofa local GTP transmission channel configuration of the CU-U sent by theCU-U, and receive second related information of a local GTP transmissionchannel configuration of the second network element sent by the secondnetwork element.

The sending unit 142 is configured to forward the first relatedinformation to a second network element, and forward the second relatedinformation to the CU-U.

In practical applications, the second acquiring unit 141, thetransmission unit 142, and the receiving unit may be implemented by acommunication interface in the apparatus for configuring a GTPtransmission channel in combination with a processor.

In addition, those skilled in the art should understand that theimplementation functions of units in the apparatus shown in FIG. 14 maybe understood with reference to the related description of the foregoingmethod.

To implement the method of the embodiments of the present disclosure,this embodiment also provides a system for configuring a GTPtransmission channel. As shown in FIG. 15, the system includes: a CU-C151 and a CU-U 152.

The CU-C 151 is configured to acquire session related information from acore network, and send the session related information to the CU-U 152through an Xn interface.

The CU-U 152 is configured to acquire the session related informationthrough the Xn interface, perform GTP transmission channel configurationby using the session related information, transmit first relatedinformation of the local GTP transmission channel configuration to asecond network element, and receive second related information of theGTP transmission channel configuration transmitted by the second networkelement.

Here, it should be noted that the specific functions of the CU-U 152 andthe CU-C 151 are described in detail above, and details are notdescribed herein.

An application scenario to which the embodiments of the presentdisclosure may be applied is an application scenario in which a LongTerm Evolution (LTE) evolved NodeB (eNB) and a 5G NodeB (gNB) coexist,as shown in FIG. 16. In this scenario, the involved network elementsinclude: an eNB, a gNB, and a core network (NG-CP/UP GW). The firstnetwork element (CU) is connected to the eNB and the gNB through an Xninterface. The second network element (DU) may be directly connected toa terminal (UE). The core network and the eNB are connected through anNG interface. The core network and the gNBs are also connected throughthe NG interface. The gNB may be divided into two logic nodes: the CUand the DU. In this scenario, the CU may be divided into a CU-U and aCU-C, so that the solution of the embodiment of the present disclosuremay be directly implemented.

For the network element shown in FIG. 16, in order to implement thefunctions of the network element, corresponding hardware devicecomponents may include a processor, a memory, a communication interface,etc.

Those skilled in the art should understand that embodiments of thepresent disclosure may be provided as methods, systems, or computerprogram products. Accordingly, the present disclosure may take the formof a hardware embodiment, a software embodiment, or a combination ofembodiments in respect of software and hardware. Moreover, the presentdisclosure may take the form of a computer program product implementedon one or more computer available storage media (including but notlimited to a disk memory, an optical memory, etc.) including computeravailable program codes.

The present disclosure is described with reference to flowchartillustrations and/or block diagrams of methods, devices (systems), andcomputer program products according to embodiments of the presentdisclosure. It should be understood that each flow and/or block in theflowchart and/or block diagram as well as a combination of flows and/orblocks in the flowchart and/or block diagram are implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general-purpose computer, a special-purposecomputer, an embedded processor, or other programmable data processingdevice to produce a machine, so that instructions executed by theprocessor of a computer or other programmable data processing deviceproduce an apparatus for implementing the functions specified in one ormore flows of the flowchart and/or in one or more blocks of the blockdiagram.

These computer program instructions may also be stored in a computerreadable memory that may direct the computer or the other programmabledata processing device to operate in a particular manner, so that theinstructions stored in the computer readable memory produce a productincluding an instruction apparatus. The instruction apparatus implementsthe functions specified in one or more flows of the flowchart and/or oneor more blocks of the block diagram.

These computer program instructions may also be loaded onto the computeror the other programmable data processing device so that a series ofoperational steps are performed on the computer or the otherprogrammable device to produce computer-implemented processing, and thusthe instructions executed on the computer or the other programmabledevice provide steps for implementing the functions specified in one ormore flows of the flowchart and/or one or more blocks of the blockdiagram.

On this basis, an embodiment of the present disclosure also provides astorage medium, specifically a computer readable storage medium storingcomputer programs which, when executed by a processor, implement theabove steps of any one method at the CU-U responsible for user planedata in the first network element, or the above steps of any one methodat the CU-C responsible for control plane data in the first networkelement.

The above are merely embodiments of the present disclosure, and are notintended to limit the scope of protection of the present disclosure.

INDUSTRIAL APPLICABILITY

According to the solutions provided by the embodiments of the presentdisclosure, the CU-C acquires session related information from the corenetwork, the CU-U acquires session related information through an Xninterface, the Xn interface is used for interaction between the CU-U andthe CU-C, the CU-U performs a GTP transmission channel configuration byusing the session related information, and transmits first relatedinformation of a local GTP transmission channel configuration to thesecond network element, and the CU-U receives second related informationof a GTP transmission channel configuration transmitted by the secondnetwork element, so that the configuration of the GTP transmissionchannel between the CU-U and the DU is achieved through the Xninterface.

1. A method for configuring a GPRS Tunneling Protocol (GTP) transmissionchannel, comprising: acquiring session related information through an Xninterface, wherein the Xn interface is used for interaction between aUser Plane Centralized Unit (CU-U) responsible for user plane data in afirst network element and a Control Plane Centralized Unit (CU-C)responsible for control plane data in the first network element;performing a GTP transmission channel configuration by using the sessionrelated information; transmitting first related information of a localGTP transmission channel configuration to a second network element; andreceiving second related information of a GTP transmission channelconfiguration transmitted by the second network element.
 2. (canceled)3. (canceled)
 4. (canceled)
 5. (canceled)
 6. The method of claim 1,wherein the step of transmitting first related information of the localGTP transmission channel configuration to a second network elementcomprises: forwarding the first related information to the secondnetwork element through the CU-C; correspondingly, the step of receivingsecond related information of the GTP transmission channel configurationtransmitted by the second network element comprises: receiving thesecond related information sent by the second network element andforwarded by the CU-C.
 7. A method for configuring a GTP transmissionchannel, comprising: acquiring session related information from a corenetwork; and sending the session related information to a CU-Uresponsible for user plane data in a first network element through an Xninterface, wherein the session related information is used by the CU-Uto perform a GTP transmission channel configuration, and the Xninterface is used for interaction between the CU-U and a CU-Cresponsible for control plane data in the first network element. 8.(canceled)
 9. The method of claim 7, further comprising: receiving firstrelated information of a local GTP transmission channel configuration ofthe CU-U sent by the CU-U, and forwarding the first related informationto a second network element; and receiving second related information ofa local GTP transmission channel configuration of the second networkelement sent by the second network element, and forwarding the secondrelated information to the CU-U.
 10. An apparatus for configuring a GTPtransmission channel, comprising: a first acquiring unit, configured toacquire session related information through an Xn interface, wherein theXn interface is used for interaction between a CU-U responsible for userplane data in a first network element and a CU-C responsible for controlplane data in the first network element; a configuration unit,configured to perform a GTP transmission channel configuration by usingthe session related information; and a transmission unit, configured totransmit first related information of the local GTP transmission channelconfiguration to a second network element, and receive second relatedinformation of a GTP transmission channel configuration transmitted bythe second network element.
 11. (canceled)
 12. (canceled)
 13. (canceled)14. (canceled)
 15. The apparatus of claim 10, wherein the transmissionunit is configured to: forward the first related information to thesecond network element through the CU-C; and correspondingly, receivethe second related information sent by the second network element andforwarded by the CU-C.
 16. An apparatus for configuring a GTPtransmission channel, the apparatus configured to implement the methodof claim 7, the apparatus comprising: a second acquiring unit,configured to acquire the session related information from the corenetwork; and a sending unit, configured to send the session relatedinformation to the CU-U responsible for the user plane data in the firstnetwork element through the Xn interface.
 17. (canceled)
 18. Theapparatus of claim 16, further comprising: a receiving unit, configuredto receive first related information of a local GTP transmission channelconfiguration of the CU-U sent by the CU-U, and receive second relatedinformation of a local GTP transmission channel configuration of asecond network element sent by the second network element; and whereinthe sending unit is configured to forward the first related informationto the second network element, and forward the second relatedinformation to the CU-U.
 19. (canceled)